rev. 0.1 3/12 copyright ? 2012 by silicon laboratories AN678 AN678 p recision 32? si 32f lash u tility c ommand -l ine p rogrammer u ser ? s g uide 1. introduction the precision32? si 32flashutility command-line pr ogrammer is a simple prog ram to enable production programming capability using the silicon labs 32-bit usb debug adapter. th is utility can also program and erase lock bytes. figure 1 shows an invocation of the command-line utility. figure 1. precision32 si32flashutility command-line programmer 2. relevant documentation precision32 application notes are listed on the following website: www.s ilabs.com/32bit-appnotes. ?? an667: getting started with the silicon labs precision32? ide ?? an669: integrat ing silicon labs sim3xxxx devi ces into the keil vision? ide
AN678 2 rev. 0.1 3. programming options the si32flashutlility has a command-line form of: si32flashutility [-options] [drive:][path]image these options consist of the following: ?? -v: verify the image after downloading to flash. ?? -i: display additional information during the programming process (i.e., verbose mode). ?? -e {0,1,2}: erase flash with three mode options. ?? -p {0,1,2}: debug port selection with three mode options. ?? -r {0,1,2}: reset during programming with three mode options. ?? -l: list the available usb debug adapters (udas). ?? -s serial: specify the usb debug adapter serial string. this section discusses each of these programming options in more detail. 3.1. download verification using the -v option flag causes the si32flashutility to verify the flash contents after the download. the command- line utility will output a download complete and verified message if the flash contents match the hex image. 3.2. verbose feedback with the -i option flag, the si32flashutility programmer will report feedback about each st ep of the programming process, as shown in figure 2. figure 2. verbose mode output
AN678 rev. 0.1 3 3.3. flash erase the -e option flag has three modes: merge, sector , and full. the default option is sector ( -e 1 ) if no option is specified. the merge option is selected with -e 0 and causes the programmer to read the current contents of the flash page selected by the hex file address, copy any contents that are not written in the hex image, erase the page, and write the merged image back to flash. this option allows developers to maintain any calibration or code constants in flash when updating code. when using the -e 1 sector erase option, the programmer will firs t erase the page selected by the hex image address before programming the contents of the hex image. the final option, -e 2 , causes the programmer to erase the entire flash before programming the hex image. 3.4. debug port this option selects the debug port of the device. the -p 0 selection is for any devices with jtag debug pins. the -p 1 option is for devices with serial wire debug pins only (sw-dp). the -p 2 option uses the serial wire protocol and is for devices with both jtag and serial wire debu g pins (swj-dp), like the sim3u1xx device family. the default option is -p 2 if no option is specified. the jtag selection ( -p 0 ) does not have provisions for jtag chaining. 3.5. reset options the utility supports th ree different reset options: none, before, and during. the defaul t option is none ( -r 0 ) if no option is specified. the none option ( -r 0 ) prevents the utility from toggling the reset pi n at any point during the programming process. the before option ( -r 1 ) allows the si32flashutility to toggle reset immedi ately before pr ogramming. this option is useful for sim3u1xx or sim3c1xx devices that may be unresponsive due to switching to a non-existent clock. using this option along with the recomm ended reset delay in th e startup code ensures the usb debug adapter will be able to communicate with the device. for the during option ( -r 2 ), the utility asserts the reset pin while attempti ng to halt the core. once the core is halted, the utility deasserts the reset pin a nd starts programming. this option ensures the debug adapter can always communicate with a device without the reset delay in the startup code for devices th at support this feature. note: the -r 2 option is unavailable for si m3u1xx and sim3c1xx devices. 3.6. usb debug adapter options the -l option flag lists the available usb debug adap ters connected to the pc or system. the -s serial option flag can then specify the usb debug adapte r the utility should use for programming.
AN678 4 rev. 0.1 4. creating hex files with the precision32 ide the si32flashutility programmer expects hex files as its input, and the precision32 ide include s a utility that can convert the gcc axf file ou tput to hex files. this objcopy utility can be found in the ..\precision32_vx.y\ide\precis ion32\tools\arm-none-eabi\bin path after installing the precision32 software package from www.silabs.com/32bit-software. more information on the usage of th is utility can be found on the code red website: http://support.code-red- tech.com/coderedwiki/outputformats. 4.1. using the objcopy utility from the ide to use the objcopy utility from the ide: 1. hold the ctrl button and left-click on the project name in the ide footer as show n in figure 3. this will open a command prompt in the project dire ctory with the pr oper paths to use the utility. figure 3. opening a project command prompt 2. type cd build_directory , where build_directory is debug by default. 3. invoke the utility: arm-none-eabi-objcopy -o ihex project_name.axf project_name.hex . in the case of this example, which uses the sim3u1xx_blinky project: arm-none-eabi-objcopy -o ihex sim3u1xx_blinky.axf sim3u1xx_blinky.hex .
AN678 rev. 0.1 5 figure 4. invoking the objcopy utility 4.2. setting the ide project to automatically generate a hex file to configure the precision32 ide project to aut omatically generate a hex file after a build: 1. right-click on the project_name in the project explorer view. 2. select properties . 3. in the c/c++ build ? settings ? build steps tab, type the following in the post-build steps ? command box: arm-none-eabi-objcopy -o ihex ${buildartifact filename} ${buildartif actfilebasename}.hex figure 5. automatically generating a hex file on project build
AN678 6 rev. 0.1 5. examples to verify the download of the sim3u1xx_blinky.hex file: si32flashutility -v sim3u1xx_blinky.hex this example is shown in figure 6. figure 6. example with flash verification to verify the download of the sim3u1xx_blinky.hex file, use verbose mode, erase the device before the download, and reset before: si32flashutility -v -i -e 2 -r 1 sim3u1xx_blinky.hex figure 7 shows an example of this ca ll to the si32flashu tility programmer. figure 7. example with flash verification, verbose mode, full device erase, and reset before options
AN678 rev. 0.1 7 n otes :
AN678 8 rev. 0.1 c ontact i nformation silicon laboratories inc. 400 west cesar chavez austin, tx 78701 tel: 1+(512) 416-8500 fax: 1+(512) 416-9669 toll free: 1+(877) 444-3032 please visit the silicon labs technical support web page: https://www.silabs.com/support/pages/contacttechnicalsupport.aspx and register to submit a technical support request. silicon laboratories and silicon labs are trademarks of silicon laboratories inc. other products or brandnames mentioned herein are trademarks or registered trademarks of their respective holders. the information in this document is believed to be accurate in all respects at the time of publication but is subject to change without notice. silicon laboratories assumes no responsibility for errors and omissions, and disclaims responsib ility for any consequences resu lting from the use of information included herein. a dditionally, silicon laboratorie s assumes no responsibility for the functioning of und escribed features or parameters. silicon laboratories reserves the right to make changes without further notice . silicon laboratories makes no wa rranty, rep- resentation or guarantee regarding the suitability of its products for any particular purpose, nor does silicon laboratories as sume any liability arising out of the application or use of any product or circuit, and s pecifically disclaims any an d all liability, including wi thout limitation conse- quential or incidental damages. silicon laborat ories products are not designed, intended, or authorized for use in applications intended to support or sustain life, or for any other application in which the failure of the silicon laboratories product could create a s ituation where per- sonal injury or death may occur. should buyer purchase or us e silicon laboratories products for any such unintended or unauthor ized ap- plication, buyer shall indemnify and hold silicon laboratories harmless against all claims and damages.
|
